Skip to main content

Multi Instance Exercise 7

Exercise 7: Multiple Multi Instance Jobs

Objective

To create a multiple Multi Instanace Jobs

Summary

Create a new schedule called, Multi Instance Job Limitation, with three property sets containing a property called CITY with a unique value in each set. Then create a workflow that Copies, Moves, and Deletes the file named after the CITY. Then have multiple instances of this workflow build.

Instructions

Create the Schedule

  1. Create a Schedule named Multi Instance Job Limitation.

Create the Multi Instance Jobs

  1. Create a Windows Job using the Command:File Copy Sub-type
  • Source: C:\Multi-Instance\IT\test.txt
  • Destination: C:\Multi-Instance\IT\[[JI.CITY]].txt
  • Frequency: Mon-Fri-N
  • Job Instance Definition:
    • CITY=HOUSTON
    • CITY=AUSTIN
    • CITY=DALLAS
  1. Create a Windows Job using the Command:File Move Sub-type
  • Source: C:\Multi-Instance\IT\[[JI.CITY]].txt
  • Destination: C:\Multi-Instance\IT\Archive\[[$SCHEDULE DATEyyyymmdd]]_[[JI.CITY]].txt
  • Frequency: Mon-Fri-N
  • Job Instance Definition:
    • CITY=HOUSTON
    • CITY=AUSTIN
    • CITY=DALLAS
  1. Create a Windows Job using the Command:File Delete Sub-type
  • File To Delete: C:\Multi-Instance\IT\[[JI.CITY]].txt
  • Frequency: Mon-Fri-N
  • Job Instance Definition:
    • CITY=HOUSTON
    • CITY=AUSTIN
    • CITY=DALLAS

Create Dependencies

  1. Create Job Dependencies so that the 3 jobs run in the following order:
  • File Copy File Move File Delete

Build the Schedule

  1. Build the Schedule On Hold.
  2. The PERT screen should show something like the following:

Enterprise Manager

Details
  1. Create a Schedule named **Multi Instance Job Limitation.
  2. Create 3 Multi-Instance Jobs (First Job below)
    • Name: FILE COPY
    • Job Type: Windows
    • Job Sub-Type: Command: File Copy
    • Primary Machine: SMATraining
    • User ID: SMATRAINING\SMAUSER
    • Source:
C:\Multi-Instance\IT\test.txt
  • Destination:
C:\Multi-Instance\IT\[[JI.CITY]].txt
  • Frequency: Mon-Fri-N
  • Job Instance Definition:
    • CITY=HOUSTON
    • CITY=AUSTIN
    • CITY=DALLAS
  1. (Second Job Below)
    • Name: FILE MOVE
    • Job Type: Windows
    • Job Sub-Type: Command: File Move
    • Primary Machine: SMATraining
    • User ID: SMATRAINING\SMAUSER
    • Source:
C:\Multi-Instance\IT\[[JI.CITY]].txt

Destination:

C:\Multi-Instance\IT\Archive\[[$SCHEDULE DATEyyyymmdd]]_[[JI.CITY]].txt
  • Frequency: Mon-Fri-N

  • Job Instance Definition:

    • CITY=HOUSTON

    • CITY=AUSTIN

    • CITY=DALLAS

      Job Dependency: Requires the FILE COPY Job

  1. (Third Job Below)
    • Name: FILE DELETE
    • Job Type: Windows
    • Job Sub-Type: Command: File Delete
    • Primary Machine: SMATraining
    • User ID: SMATRAINING\SMAUSER
    • File To Delete:
C:\Multi-Instance\IT\[[JI.CITY]].txt
  • Frequency: Mon-Fri-N

  • Job Instance Definition:

    • CITY=HOUSTON
    • CITY=AUSTIN
    • CITY=DALLAS
  • Job Dependency: Requires the FILE MOVE Job

  1. Build the Schedule On Hold.
  2. The PERT screen should show something like the following: